Screen Mapping

Theory of Operation

Screen Mapping works by identifying a Main Menu in the host system that is used as a base reference point for navigation to and from transaction screens. This is the starting point for transaction processes. The navigation process (i.e., series of keystrokes) required to proceed from a login state to the Main Menu may be automatically recorded by the system. A small visually unique portion of the main menu screen is marked for identification purposes. If required, multiple areas of the main menu may be marked. This allows the server to know that it has arrived at the requested destination.

The next step is the navigation from the main menu to the transaction screen. Transaction screens are the displays that users use to input data into the host system. Again, the navigation process (i.e., required keystrokes) to reach a screen and then return to the main menu may be automatically recorded.

When a transaction screen has been identified, the next step in the process is to identify the fields on the screen where the data will be entered. Screen fields are marked and each is given a field name. These fields may optionally be used in much the same way as ODBC fieldnames are used by the system; i.e., they may be used to create transactions by dragging the host screen’s marked fields on to an application screen. Doing this, means that the user can scan and enter all the data on the mobile device and the server already knows how to log on to the host system, how to navigate to the proper screen and where to place the collected data on the host screen, all without having to program the scripts yourself.